Statement frequency coverage: A code coverage criterion for assessing test suite effectiveness

Test suite evaluation using code coverage based metrics

Regression test suites of evolving software systems are often crucial to maintaining software quality in the long term. They have to be effective in terms of detecting faults and helping their localization. However, to gain knowledge of such capabilities of test suites is usually difficult. We propose a method for deeper understanding of a test suite and its relation to the program code it is i...

Coverage-driven Automated Compiler Test Suite Generation

A greedy approach for coverage-based test suite reduction

Software testing is an activity to find maximum number of errors which have not been discovered yet with optimum time and effort. As the software evolves the size of the test suite and grows with new test cases being added to the test suite. However, due to time and resource constraints rerunning all the test cases in the test suite is not possible, every time the software is modified, in order...

Beyond code coverage - An approach for test suite assessment and improvement

Code coverage is successfully used to guide white box test design and evaluate the respective test completeness. However, simple overall coverage ratios are often not precise enough to effectively help when a (regression) test suite needs to be reassessed and evolved after software change. We present an approach for test suite assessment and improvement that utilizes code coverage information, ...

Situation coverage に a coverage criterion for testing autonomous robots

Autonomous robots (AR) can get themselves into a wide range of situations, and they do not have a human to look after them in fine detail all the time. When we test autonomous robots, we must therefore care deeply about the range and diversity of the situations in which we have simulated and tested them に we must make sure that the situation coverage of our testing is adequate. Situation covera...